Repository navigation
deps: bump shiki from 3.23.0 to 4.0.1 - #72
Conversation
Bumps [shiki](https://github.com/shikijs/shiki/tree/HEAD/packages/shiki) from 3.23.0 to 4.0.1. - [Release notes](https://github.com/shikijs/shiki/releases) - [Commits](https://github.com/shikijs/shiki/commits/v4.0.1/packages/shiki) --- updated-dependencies: - dependency-name: shiki dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6c78dad048
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "react-virtuoso": "^4.18.1", | ||
| "remark-gfm": "^4.0.1", | ||
| "shiki": "^3.22.0", | ||
| "shiki": "^4.0.1", |
There was a problem hiding this comment.
Regenerate bun.lockb for this dependency bump
This commit changes package.json but does not update bun.lockb, which breaks every install path that uses bun install --frozen-lockfile (for example .github/workflows/ci.yml); per bun install --help, --frozen-lockfile means “Disallow changes to lockfile,” so the workflow will fail as soon as it detects the manifest/lock mismatch. Please include the lockfile update with this version bump.
Useful? React with 👍 / 👎.
Bumps shiki from 3.23.0 to 4.0.1.
Release notes
Sourced from shiki's releases.
Commits
69bec64chore: release v4.0.12060ca8chore: update deps32f35b5chore: release v4.0.0720f6d8test: restructure tests05a77f1feat: a leaner@shikijs/primitivepackage (#1251)cdca994feat!: drop Node v18 support, remove deprecated APIs (#1249)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)